CSDV3017 · Lecture 1 · 08 Jun 2026
What is
DevOps?
How It Works & Why It Matters

BTech CSE 6th Semester · School of Computer Sciences · UPES Dehradun

Faculty: Dr. Mohsin Furkh Dar
Mode: Online · MS Teams
Credits: 3
Session: Mon 14:00 – 15:00

Today's Learning Objectives

  • Understand what DevOps is and where it came from
  • Explain how the DevOps lifecycle works end-to-end
  • Identify the key benefits DevOps delivers to teams and organisations
  • Distinguish DevOps from traditional software delivery models
CSDV3017 · Summer Semester 2026 Slide 1 / 9
Setting the Stage

The Problem
DevOps Solves

Before DevOps, software teams operated in silos — and that caused serious friction.

🏗️
Development Team
Wrote code fast, pushed features frequently. Goal: ship quickly.

"It works on my machine!"
🛡️
Operations Team
Managed servers, stability, and uptime. Goal: don't break prod.

"We can't deploy until it's tested for 2 weeks."
💥
The Conflict
Dev wanted speed. Ops wanted stability. They rarely communicated. Deployments became high-risk events — infrequent and painful.
"The wall of confusion — developers throw code over the wall to operations, and operations throws it back when it breaks." — Gene Kim, The Phoenix Project
CSDV3017 · Summer Semester 2026 Slide 2 / 9
Core Definition

What is DevOps?

DevOps is a compound of two words: Development + Operations. But it is much more than just merging two teams.

Definition

DevOps is a set of practices, cultural philosophies, and tools that increases an organisation's ability to deliver applications and services at high velocity — evolving and improving products faster than organisations using traditional software development and infrastructure management processes.

🤝
Culture
Shared ownership, collaboration, and responsibility between Dev and Ops throughout the entire software lifecycle.
⚙️
Automation
Automate repetitive tasks — builds, tests, deployments — to reduce human error and increase speed.
📏
Measurement
Continuously measure performance, lead times, and failure rates to drive improvement decisions.
🔗
Sharing
Share knowledge, tools, and feedback loops — breaking down silos across the organisation.
CSDV3017 · Summer Semester 2026 Slide 3 / 9
Origins

A Brief History
of DevOps

DevOps did not appear overnight — it grew from decades of software delivery pain.

📅
2007 – 2008
Patrick Debois and Andrew Shafer discuss "Agile Infrastructure." The frustration with Dev–Ops silos reaches a tipping point.
🎤
2009
John Allspaw & Paul Hammond: "10+ Deploys per Day" at Velocity Conference. Patrick Debois coins the term DevOps and organises DevOpsDays in Ghent, Belgium.
📖
2013
Gene Kim et al. publish The Phoenix Project — a novel that explains DevOps through storytelling. Becomes a landmark text.
🌐
2016 – Present
DevOps becomes mainstream. Cloud platforms (AWS, Azure, GCP) embrace DevOps natively. DORA metrics established for measuring DevOps performance.
$ echo "DevOps = Agile + Lean + Continuous Delivery + Cloud"
→ A culture-first movement, tooled for speed and reliability
CSDV3017 · Summer Semester 2026 Slide 4 / 9
The Lifecycle

How DevOps Works:
The ∞ Loop

DevOps is visualised as an infinite loop — a continuous cycle of Plan → Code → Build → Test → Release → Deploy → Operate → Monitor, then back to Plan.

📋Plan
›
💻Code
›
🔨Build
›
🧪Test
›
📦Release
›
🚀Deploy
›
🔧Operate
›
📊Monitor
↩
🔄 Continuous Integration (CI)
Developers merge code frequently. Every commit triggers an automated build and test. Tools: Jenkins, GitHub Actions, GitLab CI.
🚢 Continuous Delivery (CD)
Code is always in a deployable state. Releases happen on demand, safely, at any time. Tools: Spinnaker, ArgoCD, AWS CodeDeploy.
👁️ Continuous Monitoring
Production systems are observed in real time. Alerts triggered on anomalies. Tools: Prometheus, Grafana, Datadog, ELK Stack.
CSDV3017 · Summer Semester 2026 Slide 5 / 9
Why Adopt DevOps

Benefits of DevOps

Organisations that adopt DevOps consistently outperform those that don't — across speed, stability, and quality (DORA State of DevOps Report).

⚡

Speed & Agility

Release features and fixes faster. High-performing teams deploy 208× more frequently than low performers.

🛡️

Reliability

Automated testing and CI/CD reduces defects reaching production. Change failure rate drops significantly.

📈

Scalability

Infrastructure as Code and cloud-native tooling allow scaling with consistent, repeatable processes.

🤝

Collaboration

Shared ownership reduces blame culture. Teams work toward common goals with unified toolchains.

🔒

Security (DevSecOps)

Security integrated from the start — "shift left" testing catches vulnerabilities early in the pipeline.

💰

Cost Efficiency

Automation reduces manual effort. Faster recovery from failures reduces downtime-related losses.

😊

Customer Satisfaction

Faster delivery of features aligned to user feedback. Shorter feedback loops improve product quality.

📉

Faster Recovery

Mean Time to Recovery (MTTR) drops dramatically with automated rollbacks and observability tools.

CSDV3017 · Summer Semester 2026 Slide 6 / 9
Measuring DevOps

DORA Metrics:
Measuring DevOps Performance

DORA (DevOps Research and Assessment) established four key metrics to evaluate DevOps effectiveness.

🚀
Deployment Frequency
How often an organisation successfully releases to production. Elite: Multiple times/day.
⏱️
Lead Time for Changes
Time from code commit to running in production. Elite: Less than 1 hour.
💔
Change Failure Rate
Percentage of changes causing production failures. Elite: 0–15%.
🔄
Mean Time to Recovery
How quickly a team recovers from a production failure. Elite: Less than 1 hour.
Elite DevOps teams deploy 208× more frequently and recover from incidents 2,604× faster than low performers. — DORA State of DevOps Report
CSDV3017 · Summer Semester 2026 Slide 7 / 9
Comparison

DevOps vs.
Traditional IT

How does DevOps differ from the traditional software delivery model across key dimensions?

Dimension Traditional IT DevOps
Team StructureDev, Ops, QA in separate silosCross-functional, shared ownership
Release CycleMonths to years (Waterfall)Days to hours (Continuous delivery)
TestingManual, end-of-cycleAutomated, continuous, "shift left"
InfrastructureManual provisioningInfrastructure as Code (IaC)
Failure ResponseBlame game, slow resolutionBlameless post-mortems, fast recovery
Feedback LoopLong (months to customer)Short (hours to days)
Risk PostureBig-bang releases = high riskSmall, frequent releases = lower risk
ToolsDisconnected, manual handoffsIntegrated toolchain (Git → CI → CD → Monitor)
CSDV3017 · Summer Semester 2026 Slide 8 / 9
Lecture Wrap-up

Key Takeaways

What you should be able to explain after today's session:

  • 01DevOps is a culture + practices + tools movement that unifies software development and IT operations to deliver value faster and more reliably.
  • 02It emerged from the Dev–Ops wall of confusion — the tension between the need for speed (Dev) and stability (Ops).
  • 03The DevOps lifecycle is a continuous ∞ loop: Plan → Code → Build → Test → Release → Deploy → Operate → Monitor.
  • 04Core practices include CI (Continuous Integration), CD (Continuous Delivery/Deployment), and Continuous Monitoring.
  • 05Benefits include faster delivery, higher reliability, better collaboration, built-in security, and measurable cost savings.
  • 06DORA metrics (Deployment Frequency, Lead Time, Change Failure Rate, MTTR) are the standard for measuring DevOps maturity.
📚
Next Session
Tue, 09 Jun — DevOps practices & history; Agile vs DevOps; Kanban & Scrum
🔗
Academic Portal
Resources & references available at mohsinfurkh.github.io/academic-portal
💬
Questions?
Raise your hand on MS Teams or drop a message in the course chat. See you Tuesday!
Dr. Mohsin Furkh Dar · CSDV3017 · UPES Dehradun Slide 9 / 9
← → Arrow keys to navigate